docs: terminology from passphrase to encryption password for managed encryption - #2102
Open
gaurav-goswamii wants to merge 5 commits into
Open
docs: terminology from passphrase to encryption password for managed encryption#2102gaurav-goswamii wants to merge 5 commits into
gaurav-goswamii wants to merge 5 commits into
Conversation
Contributor
Author
|
Closes #2070 |
lognaturel
requested changes
Sep 10, 2026
lognaturel
left a comment
lognaturel
left a comment
Member
There was a problem hiding this comment.
Thanks! A couple of change requests inline.
| --------------------------- | ||
|
|
||
| By default, Central stores form and submission attachments in its main database, but it can be configured to move these to an external object store. If you already have or plan to collect many files, storing them outside the main database can reduce database load and cost. It can also make it more practical to backup and restore the database. | ||
| By default, Central stores form and submission attachments in its main database, but it can be configured to move these to an external object store. |
Member
There was a problem hiding this comment.
Looks like an unrelated change.
| @@ -490,7 +490,7 @@ info: | |||
| * `POST /projects/…/key` to enable project managed encryption. | |||
Member
There was a problem hiding this comment.
The API docs are managed in the central-backend repo and copied over for rendering, please revert the change to central.yaml. In this case, let's not make the change at all in the API docs, the usage is clear enough for the more technical audience those docs target.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #2070
Summary
Updates the documentation terminology for Project Managed Encryption features to use "encryption password" instead of "passphrase" for consistency and clarity.
Changes Made
docs/central-encryption.rst: Updated user documentation guides to refer to "encryption password" and "encryption password hint" for project managed encryption.docs/_static/api-spec/central.yaml: Updated endpoint descriptions and feature overviews related to project managed encryption in the OpenAPI specification.central-backup.rstand system backup endpoints.Verification
make autobuild.